EpochCore Video Suite · walkthrough

Two browser apps that fix, merge, and seal video for EpochCore. Every export is sealed through the Q‑Routed™ trademark family — WORM ledger, QCCF fingerprint, QRNG entropy, three‑signature chain. No upload, no install, no Python, no ffmpeg.

Q‑Routed™ 17 quantum algorithms as HTTPS q-routed.com →
QPC™ 21 Python endpoints, Cloudflare‑fronted qpc.q-routed.com →
QTP™ Temporal lookahead + rollback qtp.q-routed.com →
RAS root · 40668c787c463ca5 · matrix epoch26matrix2025

01The stack read once

Three sibling products under the Q‑Routed™ trademark family. The video apps talk to QPC for /health, WORM ledger, and the three QPC algorithms (qccf, qrng, qverify). Everything carries the same Ed25519 + ML‑DSA‑65 (NIST FIPS‑204) envelope, chained back to a single RAS root.

Browser appyour video
→
QPC/worm + /qpc/*
→
WORM ledgerpropose · apply · verify
→
QCCFfingerprint
+
QRNGquantum entropy
+
Qverify3‑sig chain
→
You don't have to understand the envelope. Every export silently does the right thing. Open the receipt drawer if you want to see what the apps stamped on your behalf.

02Auto‑Merge Two merge2/Auto-Merge Two.html

Stitches two clips into one with a silence‑anchored seam. The vocal samples are never re‑encoded — only the visual transition and gap timing are computed. EpochCore plate covers the source corner watermark on every output frame.

  1. Open the app. The two clips for the session are pre‑loaded as clip1.mp4 and clip2.mp4. Their durations appear under each preview.
  2. Watch the auto‑detect. A 6‑agent pre‑flight swarm appears at the bottom: Lip‑sync auditor · Seam‑silence guard · Dissolve smoother · Tail‑pad sentinel · Loudness matcher · Render‑clock referee. Three more QPC agents wait below the dashed line — they fire post‑export.
  3. Preview the seam (optional). Hit Space or click ▶ Preview seam (A). You'll hear a 3 s window centered on the join. Tweak trims/fades and re‑preview as needed.
  4. A/B testing (optional). Click Snapshot → B, change params, click Swap A ↔ B to compare. A / B keys jump between saved snapshots.
  5. Merge & Export. The Conductor card and swarm light up. The encoder is WebCodecs (real MP4, H.264 + AAC) if your browser supports it, MediaRecorder (WebM) otherwise. Watch the log for codec choice.
  6. Receipt appears. Sealed entry ID, SHA‑256, QCCF fingerprint, QRNG seed, 3‑sig chain status, plus a link to the live WORM ledger. The download button is right there.
9 swarm agents Real MP4 via WebCodecs A/B preview Lip‑sync auto‑offset

Open Auto‑Merge ↗

03EpochCore Watermarker portable single file

Drop any video. The bottom‑right corner is frosted‑glass blurred over the source watermark (Gemini Veo by default), and the EpochCore mark is stamped on top with a soft cyan‑teal glow. Works on one file or a batch.

  1. Open the file. The portable bundle is a single HTML — double‑click to launch in any browser. Drop one or more videos onto the dashed zone, or click to pick.
  2. Tune (optional). Corner (BR / BL / TR / TL), plate size (% of height), edge padding, and logo glow color. Defaults are tuned for 16:9 Veo output.
  3. Watermark & Export. Each file flows through the same chain: propose → record (canvas + WebCodecs) → SHA‑256 → QCCF + QRNG → apply + verify → Qverify. A queue table shows live status per file.
  4. Download. Each completed row exposes a download link inline. The most recent successful file also surfaces in the main download button and preview.
Batch tip. Drop 8 files at once and walk away. Each gets its own sealed receipt, each is independently downloadable, all 8 entries appear in the WORM ledger.

Open Watermarker ↗ Dev version ↗

04The provenance chain every export

What gets sealed when you click export. Each call is independently signed and timestamped on QPC. The whole chain is replayable from the entry ID alone.

proposePOST /worm/propose
→ entry_id
→
renderWebCodecs MP4
→ blob
→
SHA‑256browser native
→ digest
→
QCCF + QRNGqpc/qccf, qpc/qrng
→ stamps
applyPOST /worm/apply
commit
→
verifyPOST /worm/verify
witness 2
→
Qverify3‑sig chain
Ed25519 + ML‑DSA + SLH‑DSA
→
receiptlocalStorage
+ ledger entry
Failure isn't fatal. If the network drops or QPC is offline, the export still completes — the receipt simply marks unreachable stages with a red pill. You can re‑run the seal later by feeding the SHA‑256 back to /worm/propose.

05Receipts bottom‑left pill

Both apps carry a floating "Receipts N" pill in the bottom‑left. Click to open the drawer.

  1. Click the pill. The drawer slides in from the right with up to the last 50 receipts persisted in localStorage.
  2. Click any row to expand. Full SHA‑256, entry ID, QCCF fingerprint, QRNG seed, RAS root, and timestamp appear inline.
  3. Export JSON. Pull every receipt as a single file for compliance archival.
  4. View WORM ledger. Direct link to the live ledger at qpc.q-routed.com — verify any entry you've sealed from any browser.

06Conductor live /health

Top‑right of both apps. Three dots (temporal × classical × quantum) reflect the live GET qpc.q-routed.com/health response. Polled every 30 s. Green = the backend can seal; red = exports run but receipts are unsealed.

all 3 green · qpc · NNN ms checking · qpc · in flight qpc · offline

07Cheat sheet keep open

Keyboard (Auto‑Merge)

Space Preview seam window  ·  A Jump to snapshot A  ·  B Jump to snapshot B

When to use which

If something doesn't seal